-
Notifications
You must be signed in to change notification settings - Fork 1
Container version #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
3d42a01 to
78b9da3
Compare
*) Build with docker file
podman build -f Containerfile -t fedora36-django
*) Push to quay
To Run pull from Quay
podman run -v ${PWD}:/vagrant:Z -p 8000:8000 -it <imageid> /bin/bash
<imageid> = quay.io/yarboa/django-fedora36
Removed pipeenv from gihub workflow
78b9da3 to
ee7e8dc
Compare
|
@Yarboa please add README,
|
| dnf clean all | ||
|
|
||
| RUN \ | ||
| python3 -m pip install -r requirements.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please build a version that uses pipenv - requirements.txt is not an adequate replacement.
try using Red Hat's Python s2i image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see this
https://github.com/sclorg/s2i-python-container/blob/master/3.6/README.md
It is very interesting but not clear for me,
I see an option for django pipenv and for release gunicorn option,
Could be that i need more guidance here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
|
||
| (setsid pipenv run python manage.py runserver 0.0.0.0:8000 > runserver.log 2>&1 &) | ||
| #(setsid python3 manage.py runserver 0.0.0.0:8000 > runserver.log 2>&1 )& | ||
| python3 manage.py runserver 0.0.0.0:8000 > runserver.log 2>&1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't output the logs to a file - when running in a container you want to have the logs be tracked by the runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack
*) Build with docker file
podman build -f Containerfile -t fedora36-django
*) Push to quay
To Run pull from Quay in background (detached)
podman run --rm --name django-server -d -v ${PWD}:/vagrant:Z -p 8000:8000 -it quay.io/yarboa/django-fedora36
To connect
podman exec -it $(podman ps --filter "name=django-server" --format="{{ .ID }}") /bin/bash
Removed pipeenv from gihub workflow